fix: sync manifests, unblock release-PR checks, add OpenAI submission docs - #21

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "Tracked workflow and docs files:"
git ls-files ".github/workflows/release-please.yml" "docs/versioning.md"

echo
echo "Workflow excerpt:"
sed -n '1,80p' .github/workflows/release-please.yml 2>/dev/null || true

echo
echo "Versioning excerpt:"
sed -n '1,150p' docs/versioning.md 2>/dev/null || true

echo
echo "Release-please action / input references:"
rg -n "release-please|RELEASE_PLEASE_TOKEN|skip-labeling|issues|pull-requests|contents" .github/workflows/release-please.yml docs/versioning.md

Repository: KSEGIT/Version-Sentinel

Length of output: 13214

🌐 Web query:

Release Please action issues write permission labels release PR skip-labeling

💡 Result:

To ensure Release Please functions correctly when creating pull requests and applying labels, you must configure the appropriate permissions in your GitHub Actions workflow file. Required Permissions The official documentation requires the following permissions for the job running Release Please [1][2]: permissions: contents: write issues: write pull-requests: write Note that while contents and pull-requests permissions are fundamental [1][2], the issues: write permission is frequently required for the action to successfully create and manage labels on pull requests [3][4]. Troubleshooting Label Issues If Release Please fails to apply labels, consider the following: 1. Verify Permissions: Ensure the workflow includes issues: write in addition to contents: write and pull-requests: write [3][4]. 2. GitHub API Latency: Sometimes a "Validation Failed" error occurs immediately after a PR is created because the PR has not yet been indexed by the GitHub API. Re-running the workflow typically resolves this [3]. 3. Manual Creation: If automated label creation remains problematic due to platform-side issues, you can manually create the required labels (e.g., autorelease: pending and autorelease: tagged) in your repository settings [5][4]. Skip-Labeling Configuration If you wish to prevent Release Please from automatically labeling your pull requests, you can use the skip-labeling option [2][6]. * GitHub Action usage: Set the skip-labeling input to true [2][7][6]. with: skip-labeling: true * CLI usage: Pass the --skip-labeling flag [8][9]. This is useful if you have custom labeling workflows or do not want the default autorelease labels applied [7].

Citations:

• 1: https://github.com/google-github-actions/release-please-action
• 2: https://github.com/marketplace/actions/release-please-action
• 3: Fails to create label when action runs googleapis/release-please-action#1105
• 4: GITHUB_TOKEN requires repository-projects: read to work properly googleapis/release-please-action#1072
• 5: Labels are not being correctly applied to PR using GITHUB_TOKEN googleapis/release-please-action#1074
• 6: https://github.com/googleapis/release-please-action
• 7: feat: support for skip-labeling parameter for GitHub action googleapis/release-please-action#1066
• 8: https://github.com/googleapis/release-please/blob/HEAD/docs/cli.md
• 9: https://github.com/googleapis/release-please/blob/a61fa929b42f04c6acdd6650328d3f90903b7dc5/docs/cli.md

• .github/workflows/release-please.yml#L20-L26 (this comment)
• docs/versioning.md#L109-L112

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "== repository files matching openai-submission.md =="
git ls-files | grep -F 'docs/openai-submission.md' || true

echo
echo "== current docs/openai-submission.md =="
if [ -f docs/openai-submission.md ]; then
  cat -n docs/openai-submission.md
fi

echo
echo "== searches for starter prompts and portal flow references =="
rg -n "Prompts|starter|Create plugin|New plugin|Skills only|Test cases|Privacy|Terms|platform.openai.com/plugins" docs tests README.md . || true

Repository: KSEGIT/Version-Sentinel

Length of output: 7876

🌐 Web query:

OpenAI plugins skills-only submission flow Prompts tab Create plugin submission portal

💡 Result:

As of August 2026, the plugin submission process is handled through the central plugin submission portal [1][2]. Plugins—which may include skills-only configurations, MCP-backed capabilities, or a combination of both—are the primary method for extending ChatGPT and Codex workflows [3][4][5]. Submission Flow and Portal To submit a plugin: 1. Development: Build and test your plugin in Developer Mode [1][2]. Skills-only plugins are defined by their workflow instructions, while MCP-backed plugins require an MCP server to connect to external systems [5]. 2. Submission: Access the plugin submission portal to submit your plugin for review [1][6]. The portal serves as the unified destination for managing the lifecycle of your plugin, including the initial submission, tracking status in the review queue, and receiving feedback [1][2]. 3. Review and Approval: Once submitted, your plugin enters a review queue [1][2]. You can monitor the status directly within the plugin submission portal and will receive email notifications regarding any status changes [1][2]. If rejected, you may address the feedback and resubmit [1][2]. 4. Publishing: Upon approval, you can publish the plugin via the plugin submission portal, making it available in the universal plugin directory [1][2][6]. Key Considerations - Skills-Only Plugins: These are supported for workflows that rely solely on instructions and existing tools [5]. Even for skills-only plugins, the submission and review process is managed through the same plugin submission portal used for more complex, app-backed plugins [1][2]. - Account Verification: All submissions must originate from verified individuals or organizations. You can confirm your identity and business affiliation within the general settings of the OpenAI Platform Dashboard [7]. - Updates: Once published, the plugin's metadata and configuration are locked for safety [1][2]. To update an existing plugin, you must create a new draft version in the portal and submit it for a fresh review [1][2].

Citations:

• 1: https://developers.openai.com/apps-sdk/deploy/submission
• 2: https://developers.openai.com/plugins/deploy/app-review
• 3: https://help.openai.com/en/articles/20001256-plugins-in-chatgpt-and-codex
• 4: https://developers.openai.com/codex/plugins
• 5: https://developers.openai.com/plugins/concepts/plugins
• 6: https://developers.openai.com/plugins/build/plugins
• 7: https://developers.openai.com/apps-sdk/app-submission-guidelines

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "== repo files around docs =="
git ls-files | sed -n '1,120p' | grep -E '(^docs/|^README|version|hook|plugin|submission)' || true

echo
echo "== docs/openai-submission.md lines 1-80 =="
if [ -f docs/openai-submission.md ]; then
  cat -n docs/openai-submission.md | sed -n '1,80p'
else
  fd -a 'openai-submission.md' .
fi

echo
echo "== searches for skills/openai/submission wording =="
rg -n "Skills|submit|forces|must guarantee|must verify|live registry|registry check|hook guarantee" . --glob '!node_modules' --glob '!dist' --glob '!build' || true

echo
echo "== package/plugin references =="
rg -n "Version Sentinel|version sentinel|OpenAI Skills|developers.openai|plugins/deploy/submission|force|guide|instruct" . --glob '!node_modules' --glob '!dist' --glob '!build' | sed -n '1,220p' || true

Repository: KSEGIT/Version-Sentinel

Length of output: 14763

🌐 Web query:

developers.openai.com plugins deploy submission OpenAI Skills submit only workflow guide vs enforce language

💡 Result:

As of August 7, 2026, ChatGPT Plugins have been deprecated and are no longer supported [1][2]. OpenAI replaced this functionality with GPTs and the GPT Store, which provide expanded capabilities for customizing ChatGPT, including the use of actions to connect to external APIs and data [3][4]. Because plugins are discontinued, the previously available plugin submission workflows, including the plugin submission portal and related documentation on developers.openai.com, are obsolete [1][2]. Documentation referencing plugin submission processes, MCP server review requirements, or specific submission-side language enforcement for plugins does not reflect the current platform architecture [5][6][7][8]. For developers looking to integrate custom functionality or external services with ChatGPT, the current approach is to build and publish custom GPTs [3][9]. Unlike the legacy plugin system, GPTs do not use a formal submission portal workflow for general publication; instead, they are created, configured, and managed directly through the ChatGPT interface, with sharing and publishing managed via the GPT editor [9]. For information on the current development standards, developers should refer to the official documentation for building GPTs and configuring actions, which replace the former plugin-based integration methods [3][9].

Citations:

• 1: https://www.openai.com/blog/chatgpt-plugins
• 2: https://community.openai.com/t/error-plugins-are-no-longer-supported/715523
• 3: https://www.zdnet.com/article/on-march-19-chatgpt-plugins-get-replaced-by-gpts-heres-why-and-what-it-means-to-you/
• 4: https://community.openai.com/t/are-custom-gpts-replacing-plugins/590048/2
• 5: https://developers.openai.com/plugins/deploy/app-review
• 6: https://developers.openai.com/plugins/deploy/submission-errors
• 7: https://developers.openai.com/plugins/quickstart
• 8: https://developers.openai.com/apps-sdk/deploy/submission
• 9: https://help.openai.com/en/articles/8554397-creating-and-editing-gpts

🌐 Web query:

OpenAI Codex plugins PreToolUse hooks skills submission review requirements

💡 Result:

In OpenAI's Codex ecosystem, plugins are declarative packages used to bundle skills, connectors (MCP servers), and lifecycle hooks into reusable units [1][2][3]. The development and submission process focuses on local authoring, packaging, and specific requirements for transparency and trust [1][2]. Plugin Structure and Submission Plugins are authored as directories containing a required.codex-plugin/plugin.json manifest [2][3]. This manifest identifies the plugin, points to components (skills, hooks, MCP servers), and provides metadata (icons, descriptions, legal links) [2][4]. 1. Local Development: Authors typically use the built-in @plugin-creator skill to scaffold the required directory structure and manifest [2][5]. Iteration is done locally before packaging for distribution [1][3]. 2. Distribution: Reusable skills, connectors, or bundled workflows are packaged into plugins [1]. Marketplace entries (typically a JSON catalog) turn these directories into installable units [3]. 3. Review Requirements: When submitting plugins for broader platform distribution, developers must adhere to specific submission flows that include MCP checks, test case requirements, and compliance with permissions and privacy policy standards [6]. PreToolUse Hooks The PreToolUse hook is a lifecycle event that allows developers to intercept tool calls—primarily Bash/shell commands—before they are executed by the agent [7][8]. - Functionality: When a plugin is enabled, it can bundle PreToolUse hooks [7][9]. These hooks run alongside user, project, and managed hooks [10][9]. - Governance and Trust: Plugin-bundled hooks are considered non-managed [7][9]. They are not automatically trusted upon installation [7][9]. Codex skips these hooks until the user explicitly reviews and trusts the specific hook definition via the /hooks interface in the CLI [7][11]. - Technical Limitations: As of current specifications, PreToolUse hooks primarily intercept the shell (Bash) tool [8]. While intended to provide governance, they operate with specific constraints—for example, they cannot rewrite tool inputs or interpose interactive human confirmation flows directly; they function mainly to permit or deny execution [8]. Key Development Resources - Plugin Manifest:.codex-plugin/plugin.json [2][9]. - Hook Configuration: Defaults to hooks/hooks.json or can be specified in the manifest [7][9]. - CLI Utilities: The Codex CLI is the primary interface for inspecting hooks, reviewing/trusting definitions, and managing plugin installations [7][6]. - Official Documentation: Detailed requirements for packaging and submission are available at developers.openai.com/codex/plugins and related build guides [2][6][9].

Citations:

• 1: https://developers.openai.com/codex/skills
• 2: https://developers.openai.com/codex/plugins/build
• 3: https://harnez.ai/posts/plugin-marketplace-architecture/
• 4: https://github.com/openai/codex/blob/31519549/codex-rs/core-plugins/src/manifest.rs
• 5: https://github.com/openai/codex/blob/main/codex-rs/skills/src/assets/samples/plugin-creator/SKILL.md
• 6: https://developers.openai.com/codex/plugins
• 7: https://developers.openai.com/codex/hooks
• 8: https://agenticcontrolplane.com/blog/codex-cli-hooks-reference
• 9: https://developers.openai.com/plugins/build/plugins
• 10: https://learn.chatgpt.com/docs/hooks.md
• 11: https://learn.chatgpt.com/docs/hooks

🌐 Web query:

site:docs.claude.com plugins submit skills hook enforcement skills only

💡 Result:

There is no publicly documented feature, setting, or command called plugins submit skills hook enforcement skills only within the Claude developer platform or documentation. Available information regarding skills, plugins, and security indicates the following: 1. Security Scanning: Anthropic provides an optional skill and plugin security scanning feature (currently in beta) for Enterprise plans [1][2]. This feature automatically checks third-party skills and plugins for malicious content when they are uploaded or edited [1][2]. 2. Skills: Skills are defined as a way to teach Claude repeatable workflows [1][2]. Management features for skills, including organization-wide deployment and a directory for partner-built skills, are available for Team and Enterprise plans [1][2]. 3. Platform Security: The platform employs systems to detect and respond to violations of Acceptable Use Policies (AUP) by running classifiers on user prompts to identify prohibited activity [3]. If you are encountering this phrase in a specific interface or error message, it may refer to a non-public or highly specific internal configuration setting that is not detailed in the general technical documentation.

Citations:

• 1: https://docs.claude.com/id/release-notes/claude-apps
• 2: https://docs.claude.com/zh-TW/release-notes/claude-apps
• 3: https://docs.claude.com/fr/resources/claude-3-model-card.md

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "Repository files matching docs/openai-submission.md:"
if [ -f docs/openai-submission.md ]; then
  wc -l docs/openai-submission.md
  sed -n '1,130p' docs/openai-submission.md
else
  fd -a 'openai-submission\.md$' .
fi

echo
echo "Search for nearby policy/availability guidance:"
rg -n "Privacy URL|Terms URL|worldwide|availability|privacy|terms|Policy|Submit|deployment|deployment/submission|developers.openai.com" docs -S || true

echo
echo "Search for privacy/terms files:"
git ls-files | rg '(^|/)(PRIVACY|TERMS|LICENSE|README)\.(md|txt)$' || true

Repository: KSEGIT/Version-Sentinel

Length of output: 6652

🌐 Web query:

OpenAI plugins availability worldwide regions requirement privacy terms URLs openai.com plugins/deploy/submission

💡 Result:

As of August 7, 2026, the original "ChatGPT Plugins" feature has been fully deprecated and retired [1][2][3]. While some documentation or UI references may appear to persist or transition into newer integration frameworks, the legacy plugin platform—which utilized ai-plugin.json manifest files—ceased functioning in April 2024 [1][2]. Current Availability and Status: - Legacy Plugins: These are no longer supported [1][2]. Conversations relying on them stopped working as of April 9, 2024 [1][2]. - Modern Alternatives: OpenAI has replaced the plugin functionality with more robust tools, primarily GPTs, GPT Actions, and native integrations (such as ChatGPT Search and Data Analysis) [1][4]. Developers and users are encouraged to migrate legacy plugin workflows to GPT Actions, which allow for similar API connectivity but operate within the updated GPT builder interface [5][6][7]. - Current "Plugins" terminology: In 2026, you may encounter references to "plugins" in the context of ChatGPT Work or Codex environments [8][9]. These are distinct from the deprecated legacy ChatGPT plugins. They function as a way to bundle skills, apps, and connectors for specific workflows within these professional environments [8][9]. Requirements and Privacy: - For the modern integrations available in ChatGPT Work or Codex, capabilities are managed through the plugin directory within those specific platforms [8][9]. - Privacy and terms for these integrations are handled on a per-app basis [8]. When using a connection or app, users are subject to the specific terms and privacy policies of the underlying third-party service [9]. - Access to these features is subject to your specific plan (e.g., ChatGPT Work), workspace settings, administrative controls, and regional availability [8][10]. Administrative controls allow workspace admins to manage installation and permissions [8]. If you are looking to deploy or manage modern capabilities, you should reference the official documentation for ChatGPT Work or Codex, rather than the legacy developer documentation for the original ChatGPT plugin beta [8][9].

Citations:

• 1: https://chatai.guide/features/chatgpt-plugins-legacy/
• 2: https://community.openai.com/t/error-plugins-are-no-longer-supported/715523
• 3: https://www.openai.com/blog/chatgpt-plugins
• 4: https://au.lifehacker.com/ai/10621/news/why-openai-replaced-chatgpt-plugins-with-gpts
• 5: https://community.openai.com/t/i-migrated-my-plugin-to-gpt-here-is-what-i-have-found-with-oauth-and-openapi/486664
• 6: https://community.openai.com/t/how-to-migrate-from-chatgpt-plugins-to-actions-solving-oauth-failures/480400/1
• 7: https://bestremotetools.com/migrate-chatgpt-plugins-to-custom-gpts-step-by-step-2026/
• 8: https://help.openai.com/en/articles/20001256-plugins-in-chatgpt-and-codex
• 9: https://developers.openai.com/codex/plugins
• 10: https://openai.com/index/codex-for-every-role-tool-workflow/

🌐 Web query:

developers.openai.com plugins deploy submission policy regional availability privacy terms URLs

💡 Result:

As of August 7, 2026, the original ChatGPT Plugins beta (introduced in 2023) has been deprecated and fully shut down [1][2]. While some developer documentation pages related to "plugins" remain accessible on the OpenAI developer site [3][4][5][6][7], these pages describe a new, evolved platform architecture that integrates Model Context Protocol (MCP) servers, apps, and skills [3][8]. In this current ecosystem, "plugins" function as a container for apps, skills, and app templates within a unified directory [8]. Key details regarding this updated infrastructure include: Deployment and Submission: Developers submit plugins through the OpenAI plugin submission portal [3][4]. The submission process involves scanning an MCP server, validating tool metadata, and providing required listing information [3][7]. Submissions are reviewed by OpenAI before they can be published to the directory [3][4]. Plugins must meet specific guidelines, including stability, security, and the provision of clear, published privacy policies, terms of service, support URLs, and website links [6][7]. Regional and Access Availability: Availability of plugins is determined by a combination of factors, including the user's plan (e.g., ChatGPT Plus, Enterprise), workspace settings, role-based controls, and regional restrictions [8][9]. Workspace administrators have the authority to enable or disable specific plugins and apps for their users [8][9]. Integration with external services may be limited by geo-restrictions or administrative settings, which can cause connection buttons to appear greyed out or disabled [8]. Privacy and Terms: All plugin submissions must include publicly accessible URLs for a privacy policy and terms of service [7]. These policies must explicitly cover data collection, purposes of use, recipients, retention, and user controls [6]. If you are looking for information on the original 2023 plugin beta, please note that it was officially decommissioned in April 2024 [1][2]. The current system relies on MCP-backed integrations as the primary path for extending ChatGPT and Codex capabilities [8][2].

Citations:

• 1: https://chatai.guide/features/chatgpt-plugins-legacy/
• 2: https://www.getdrio.com/blog/chatgpt-plugins-vs-custom-gpts
• 3: https://developers.openai.com/plugins/deploy/submission
• 4: https://developers.openai.com/plugins/deploy/app-review
• 5: https://developers.openai.com/plugins
• 6: https://developers.openai.com/plugins/app-guidelines
• 7: https://developers.openai.com/plugins/deploy/submission-errors
• 8: https://help.openai.com/en/articles/20001256-plugins-in-chatgpt-and-codex
• 9: https://chatgpt.com/features/plugins/

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "== files =="
git ls-files | rg '(^docs/|skills/version-sentinel|VERSION|README|marketplaces|openai-submission|version-sentinel)' || true

echo
echo "== relevant doc excerpts =="
sed -n '1,140p' docs/openai-submission.md 2>/dev/null || true
echo "---"
sed -n '90,130p' docs/marketplaces.md 2>/dev/null || true

echo
echo "== repository paths around version-sentinel scripts =="
if [ -d skills/version-sentinel ]; then
  find skills/version-sentinel -maxdepth 3 -type f | sort
fi
if [ -d scripts ]; then
  find scripts -maxdepth 3 -type f | sort
fi

echo
echo "== references to skills/version-sentinel/scripts in docs =="
rg -n "skills/version-sentinel|version-sentinel|scripts/|workflow |hook|plugin marketplace|marketplace add|openai|submission" docs -S || true

echo
echo "== if dependency sentinel exists, package manifests/scripts =="
fd -t f . skills/version-sentinel scripts 2>/dev/null | sort | sed -n '1,120p'

Repository: KSEGIT/Version-Sentinel

Length of output: 27676

🌐 Web query:

OpenAI Plugins Directory Submit plugins skill package assets referenced files self-contained bundle documentation

💡 Result:

As of August 7, 2026, it is important to distinguish between the legacy "ChatGPT Plugins" (which were officially deprecated and replaced by GPTs in early 2024 [1][2][3]) and the current "Plugins" infrastructure supported for Codex and related development platforms [4][5]. The legacy ChatGPT Plugins were discontinued in March/April 2024, and OpenAI now directs developers to build GPTs for ChatGPT-based functionality [1][6][7]. However, OpenAI maintains a "Plugins" developer framework for Codex and other surfaces [4][5], which continues to use a specific packaging and submission process. Plugin Packaging and Assets To package a plugin for this current infrastructure, you must structure your project as a self-contained bundle [8][9]. The core requirements include: 1. Manifest File: Every plugin must contain a manifest file at.codex-plugin/plugin.json [8][9]. This is the required entry point for the plugin [8]. 2. Directory Structure: Recommended practice is to keep all assets at the plugin root [9]. Common components include: - skills/: A directory for bundled skills [8][9]. - assets/: A folder for visual assets like composerIcon, logo, and screenshots [8][9]. -.mcp.json: Configuration for included Model Context Protocol (MCP) servers [8][9]. -.app.json: Used for mapping registered MCP server connections [8][9]. - hooks/: For lifecycle hooks [8][9]. 3. Referencing Files: All file paths in your manifest should be relative to the plugin root and start with./ (e.g.,./assets/logo.png) [8][10]. Visual assets such as icons and screenshots must point to valid files within the plugin archive [10]. Plugin Submission To publish a plugin to the universal Plugins Directory: 1. Development: Build and test your plugin (including skills, MCP servers, and UI) until it is stable in developer mode [11][12][5]. 2. Submission Portal: Use the official plugin submission portal to create a new submission [4][11]. 3. Review: You must provide required metadata, including the plugin name, description, branding assets, privacy policy/terms of service URLs, and test cases [11][13]. 4. Approval: Once submitted, OpenAI reviews the plugin against their guidelines [11][12]. After approval, you can choose to publish the plugin from the portal to make it available in the Plugins Directory [4][14]. For detailed technical specifications regarding the plugin manifest schema and submission requirements, refer to the official OpenAI developer documentation for Plugins and Codex [4][8][10].

Citations:

• 1: https://www.zdnet.com/article/on-march-19-chatgpt-plugins-get-replaced-by-gpts-heres-why-and-what-it-means-to-you/
• 2: https://au.lifehacker.com/ai/10621/news/why-openai-replaced-chatgpt-plugins-with-gpts
• 3: https://knowtechie.com/openai-chatgpt-plugins-gpts/
• 4: https://developers.openai.com/plugins/deploy/submission
• 5: https://developers.openai.com/plugins/quickstart
• 6: https://www.openai.com/blog/chatgpt-plugins
• 7: https://community.openai.com/t/error-plugins-are-no-longer-supported/715523
• 8: https://developers.openai.com/plugins/build/plugins
• 9: https://developers.openai.com/codex/plugins/build
• 10: https://github.com/openai/codex/blob/main/codex-rs/skills/src/assets/samples/plugin-creator/references/plugin-json-spec.md
• 11: https://developers.openai.com/plugins/deploy/app-review
• 12: https://developers.openai.com/plugins/app-guidelines
• 13: https://developers.openai.com/plugins/deploy/submission-errors
• 14: https://developers.openai.com/apps-sdk/deploy/submission

• docs/openai-submission.md#L51-L56 (this comment)
• docs/openai-submission.md#L98-L104
• docs/marketplaces.md#L115-L119

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "== file excerpt =="
cat -n docs/openai-submission.md | sed -n '1,130p'

echo
echo "== relevant docs links/portal refs =="
rg -n "Testing tab|expected result|artifact|BLOCKED|vs-record|/vs-record|intentional:<reason>|developers.openai.com|deployment" docs/openai-submission.md README.md 2>/dev/null || true

echo
echo "== scripts/vs-record existence =="
if [ -d scripts ]; then
  find scripts -maxdepth 2 -type f -print
else
  echo "no scripts directory"
fi
[ -x scripts/vs-record.sh ] && echo "exe" || true [ -f scripts/vs-record.sh ] && sed -n '1,160p' scripts/vs-record.sh || true

Repository: KSEGIT/Version-Sentinel

Length of output: 9632

🌐 Web query:

OpenAI plugins deployment submission testing tab expected result fixture data OpenAI Skills submission tests

💡 Result:

OpenAI plugins have been officially deprecated and are no longer supported [1][2]. They have been replaced by GPTs [3][4]. For historical context regarding the plugin submission process, the submission portal required developers to provide specific test case data to ensure quality and safety before publication [5][6]. This process included the following requirements for test cases: 1. Quantity: Developers were required to submit exactly five positive test cases and three negative test cases [5][6]. 2. Positive Test Case Components: Each positive test case required a user prompt, the expected tool/skill/workflow behavior, the expected result shape, and the specific test account or fixture data needed to reproduce the result [5]. 3. Negative Test Case Components: Negative test cases required a user prompt or scenario, as well as the expected refusal, clarification, or safe fallback behavior, including an explanation of why the plugin should not complete the requested action [5]. 4. Review Expectations: Reviewers evaluated these cases without internal context, meaning developers had to ensure that provided demo credentials could complete tests without requirements like MFA, SMS, email confirmation, or private-network access [5]. While tools and skills remain part of the broader OpenAI ecosystem (e.g., in the context of GPTs and Agent Skills), the specific plugin submission portal and its associated test fixture requirements are no longer active [1][3][2].

Citations:

• 1: https://www.openai.com/blog/chatgpt-plugins
• 2: https://community.openai.com/t/error-plugins-are-no-longer-supported/715523
• 3: https://au.lifehacker.com/ai/10621/news/why-openai-replaced-chatgpt-plugins-with-gpts
• 4: https://knowtechie.com/openai-chatgpt-plugins-gpts/
• 5: https://developers.openai.com/plugins/deploy/submission
• 6: https://developers.openai.com/plugins/deploy/submission-errors